Repository navigation
Focus image documentation on using the SDK - #13
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The image quickstart and API reference mixed usage instructions with details about preprocessing, asset hashes, runtime sharing, and native cleanup. This makes it harder to find how to install the image dependencies, pass images, or read a result.
Replace that prose with examples and concise API descriptions across both READMEs, the Python reference, and public docstrings. Remove the unexplained
max_tokens=128setting from examples and simplify the adjacent base-interpreter wording.Validation: strict MkDocs build passed; example syntax and documentation anchors checked; both README image sections match apart from link destinations. Python ASTs are identical after removing docstrings, confirming no runtime behavior changes.